Problem

Fixes #12572
Parent: #12394

When a user defines a config property like where at the top level of a generic test:

data_tests:
  - unique:
      where: "valid_to is null"

dbt was raising MissingArgumentsPropertyInGenericTestDeprecation, which misleads the developer into moving where under arguments: — which is wrong. The correct fix is to move it under config:.

Root Cause

In TestBuilder.extract_test_args(), the check for missing arguments property did not distinguish between actual test arguments and known config properties (CONFIG_ARGS like where, severity, tags, etc.). Any top-level key that wasn't config, column_name, description, or name triggered the wrong deprecation.

Fix

1. Exclude CONFIG_ARGS from the missing-arguments check in extract_test_args() so that known config properties don't trigger MissingArgumentsPropertyInGenericTestDeprecation

2. Emit PropertyMovedToConfigDeprecation for each CONFIG_ARGS key found at the root level of the test definition, guiding the developer to move it under config:

Test

Added TestMissingArgsVsPropertyMovedToConfig in tests/functional/deprecations/test_deprecations.py which verifies:

• PropertyMovedToConfigDeprecation fires for where at top level
• MissingArgumentsPropertyInGenericTestDeprecation does NOT fire

cc @dbeatty10